Admission control and load balancing

ABSTRACT

Certain aspects of the present disclosure relate to methods and apparatus for wireless communication, and more particularly, to methods and apparatus to enable a node to be aware of active services and context for a mobile device in order to determine the load balancing and admission control for the services. For example, in certain aspects, a mobile device for managing at least one data flow between a core network and the mobile device may determine whether at least one of the data flow or a service related to the data flow should be reported and send a report to a first node based on the determination. The report may identify at least one of the data flow or service and indicates a packet data network (PDN) connection or bearer associated with the service or data flow.

This application is a divisional application of U.S. patent applicationSer. No. 14/599,144 entitled “ADMISSION CONTROL AND LOAD BALANCING”,filed Jan. 16, 2015, which claims benefit of U.S. Provisional PatentApplication Ser. No. 62/039,221, entitled “ADMISSION CONTROL AND LOADBALANCING,” filed Aug. 19, 2014, which are assigned to the assignee ofthe present application and hereby expressly incorporated by referenceherein in their entirety.

FIELD

The present disclosure relates generally to wireless communication, andmore particularly, to methods and apparatus for routing data between amobile device and core network using different communication links.

BACKGROUND

Wireless communication systems are being developed with the goal ofenabling new services and devices, which will offer new userexperiences. One approach to achieve this is to leverage multipleexisting radio access technologies (RATs), for example, using acombination of features from wireless wide area networks (e.g., 3G andLTE) and wireless local area networks (e.g., based on WiFi andmillimeter wave (mmW)). This approach may help speed development andtake advantage of different benefits provided by the different RATs.

One challenge with a system that utilizes multiple RATs is how tooptimally route data between a core network and a user, given thedifferent paths offered by the different RATs.

SUMMARY

Certain aspects of the present disclosure provide a method of wirelesscommunication by a mobile device for managing at least one data flowbetween a core network and the mobile device. The method generallyincludes determining whether at least one of the data flow or a servicerelated to the data flow should be reported, and sending a report to afirst node based on the determination, wherein the report identifies atleast one of the data flow or service and indicates a packet datanetwork (PDN) connection or bearer associated with the service or dataflow.

Certain aspects of the present disclosure provide a method of wirelesscommunication by a second node for managing at least one data. Themethod generally includes determining a data flow is active for a beareror a packet data network (PDN) connection, deciding, based on one ormore service requirements of the data flow, whether to serve the dataflow at the second node or a first node, and sending, to the first node,a request for admission of the data flow.

Certain aspects of the present disclosure provide a method of wirelesscommunication by a first node for performing admission control on atleast one data flow. The method generally includes receiving, from asecond node, a request for admission of the at least one data flow for abearer comprising a plurality of data flows, evaluating availability ofresources at the first node to serve the at least one data flow with thebearer, and indicating to the second node whether admission is grantedto the at least one data flow based at least in part on the evaluatedavailability of resources.

Certain aspects of the present disclosure provide a method of wirelesscommunication by a first node. The method generally includes determiningthat at least one data flow is active for an existing bearer or a newpacket data network (PDN) connection, wherein the data flow has anassociated aggregation layer of a protocol stack of the first node,evaluating the availability of resources at the first node to serve thedata flow, wherein the evaluating relates to resources managed by atleast one protocol layer that is below the associated aggregation layerof a protocol stack of the first node, and transmitting, to a secondnode, a message indicating the availability of resources at the firstnode for data flows associated with the second node and for data flowsnot associated with the second node.

Aspects also provide various apparatus, systems, computer programproducts, and processing systems for performing the operations describedabove.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example wireless environment, in accordance withcertain aspects of the present disclosure.

FIGS. 2A and 2B illustrate example protocol layers for control plane anduser plane routing, in accordance with certain aspects of the presentdisclosure.

FIG. 3 illustrates an example multi-connectivity protocol stack, inaccordance with aspects of the present disclosure.

FIG. 4 illustrates example offload configuration, in accordance withaspects of the present disclosure.

FIG. 5 illustrates example user plane (U-plane) splittingconfigurations, in accordance with aspects of the present disclosure.

FIG. 6 illustrates example control plane (C-plane) logical architectureoptions, in accordance with aspects of the present disclosure.

FIG. 7 illustrates example control place (C-plane) Non-Access Stratum(NAS) logical architecture options, in accordance with aspects of thepresent disclosure.

FIG. 8 illustrates an example call flow diagram of a mobile device, amaster base station, and a secondary base station, in accordance withaspects of the present disclosure.

FIG. 9 illustrates an example call flow diagram for providing a set ofservice and UE context to a mobility management entity (MME), inaccordance with certain aspects of the present disclosure.

FIG. 10 illustrates an example call flow diagram for providing a set ofservice and UE context to a RAN, in accordance with certain aspects ofthe present disclosure.

FIG. 11 illustrates example operations for managing at least one dataflow between a core network and a mobile device, in accordance withcertain aspects of the present disclosure.

FIG. 12 illustrates example operations for managing at least one dataflow, in accordance with certain aspects of the present disclosure.

FIG. 13 illustrates example operations for performing admission controlon at least one data flow, in accordance with certain aspects of thepresent disclosure.

FIG. 14 illustrates example operations for performing load balancing, inaccordance with certain aspects of the present disclosure.

FIG. 15 illustrates a block diagram of an example user equipment, inaccordance with aspects of the present disclosure.

FIG. 16 illustrates a block diagram of an example base station, inaccordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Aspects of the present disclosure provide techniques that may be used toroute data between a core network and a user equipment (UE) connectedvia multiple radio access technologies (RATs). In some cases, an entitymaking admission control or load balancing decisions (to routed databetween the multiple RATs) may consider which particular services areactivated.

Aspects of the present disclosure may be applied to a wide variety ofdifferent types of mobile devices communicating via a wide variety ofdifferent RATs. Different terminology may be used to refer to mobiledevices. For example, in some cases depending on the RAT(s) supportedthereby, a mobile device may be referred to as a wireless device, userterminal (UT), access terminal (AT), user equipment (UE), station,mobile station, wireless station, wireless node, or the like. Similarly,different terminology may be used to refer to a base station thatprovides services to a mobile device, such as access to a core network.For example, in some cases depending on the RAT(s) supported thereby, abase station may be referred to as an access point (AP), a node B, anenhanced Node B (eNodeB), or simply an eNB.

In certain examples that follow, a mobile device is referred to as a UEand base station are referred to as eNBs. Such references are not meantto limit aspects of the present disclosure to any particular RAT orRATs, but are merely to help describe illustrative examples meant tofacilitate understanding.

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well-known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, modules, components,circuits, steps, processes, algorithms, etc. (collectively referred toas “elements”). These elements may be implemented using hardware,software, or combinations thereof. Whether such elements are implementedas hardware or software depends upon the particular application anddesign constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented with a “processing system”that includes one or more processors. Examples of processors includemicroprocessors, microcontrollers, digital signal processors (DSPs),field programmable gate arrays (FPGAs), programmable logic devices(PLDs), state machines, gated logic, discrete hardware circuits, andother suitable hardware configured to perform the various functionalitydescribed throughout this disclosure. One or more processors in theprocessing system may execute software. Software shall be construedbroadly to mean instructions, instruction sets, code, code segments,program code, programs, subprograms, software modules, applications,software applications, software packages, firmware, routines,subroutines, objects, executables, threads of execution, procedures,functions, etc., whether referred to as software/firmware, middleware,microcode, hardware description language, or otherwise.

Accordingly, in one or more exemplary embodiments, the functionsdescribed may be implemented in hardware, software, or combinationsthereof. If implemented in software, the functions may be stored on orencoded as one or more instructions or code on a computer-readablemedium. Computer-readable media includes computer storage media. Storagemedia may be any available media that can be accessed by a computer. Byway of example, and not limitation, such computer-readable media cancomprise RAM, ROM, EEPROM, PCM (phase change memory), flash memory,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Disk and disc, asused herein, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk and Blu-ray disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of computer-readable media.

An Example Wireless Environment

FIG. 1 illustrates an example wireless environment 100, in which aspectsof the present disclosure may be utilized to manage data flows between acore network and a wireless device, such as UE 110.

As illustrated, UE 110 may be capable of communicating with multiplebase stations, such as a master eNodeB (MeNB) 120 and a secondary eNodeB(SeNB) 130. MeNB 120 and SeNB 130 may communicate via the same RAT ordifferent RATs. For example, MeNB 120 may communicate via a wirelesswide area network (WWAN) protocol (e.g. LTE) while SeNB 130 maycommunicate via a wireless local area network (WLAN) protocol (e.g.,WiFi).

As used herein, the term MeNB generally refers to an eNB that terminatesan S1-MME (Mobility Management Entity) control plane for the UE, whilethe term SeNB generally refers to an eNB serving the UE that is not theMeNB. An S1 connection may be used by the MeNB or SeNB to communicatewith the core network (CN), for example via a CN gateway (GW) 140. Forexample, the S1 interface may include an S1-U interface, which servesthe data plane between the MeNB or SeNB and the CN GW, and an S1-MME,which serves the control plane.

In certain aspects, the MeNB may be connected to one or more SeNBs toserve a UE via multi-connectivity. The MeNB and SeNB may communicatewith one another via a backhaul connection 150 (e.g., an X2 connection).The backhaul connection need not be direct but may be routed through oneor more intermediate nodes (e.g., an MME, an interworking gatewayfunction, or a router). The number of SeNBs may be limited, depending onthe capabilities of the UE. The MeNB may coordinate mobility anduser-plane (U-plane) split procedures within the corresponding operatornetwork. The MeNB may be considered as “access agnostic,” meaning it maysupport any type of RAT both to serve the UE and also for managing theUE configuration of a U-plane split with one or more SeNBs. For example,an MeNB may utilize a common U-plane anchored in the operator's corenetwork (CN) in order to enable procedures to manage the U-plane splitvia multiple RATs, as described herein.

The SeNB may be utilized as a source of supplemental capacity for theMeNB and may also use a different RAT (from the RAT of the MeNB) toserve the UE. According to aspects of the present disclosure, an SeNB islimited to serving a UE and in most cases may not be used to control theUE configuration of the U-plane split. Having the SeNB as a supplementalcapacity for the MeNB may provide an opportunistic and energy efficientoperation, which may be initiated by the UE's user or the networkoperator.

The SeNB may be loosely or tightly coupled with the MeNB, depending onbackhaul bandwidth capabilities and latency requirements. For example,an SeNB that is considered tightly coupled with an MeNB may have theSeNB's connection to the UE substantially managed by the MeNB. On theother hand, an SeNB that is considered loosely coupled with an MeNB mayleave the SeNB's connection to the UE under the control of the SeNBsubject to, for example, general requirements such as Quality of Service(QoS) from the MeNB. For example, an SeNB with a high-capacity andlow-latency backhaul link to an MeNB may be tightly coupled with theoperations of the MeNB. The SeNB may be used as a supplemental downlink(SDL) or as an additional cell for both uplink (UL) and DL. In somecases, the SeNB may be used to help achieve supplemental mobilityrobustness of the MeNB, for example, for mission critical applications.For example, the SeNB may provide a redundant path for delivery ofcritical information and may also provide a fast failover (to the SeNB)in the event the MeNB experiences a radio link failure (RLF).

Multi-connectivity (MC) generally refers to a mode of operation whereina UE is connected (e.g., radio resource control (RRC) connected) to anMeNB and at least one SeNB, as illustrated in FIG. 1. FIG. 1 shows aspecific example of MC, with two different eNBs, that may be referred toas dual connectivity (DC). In MC, a group of serving cells associatedwith the MeNB, including a primary cell (PCell) and optionally one ormore secondary cells (SCells), may be referred to as a master cell group(MCG). Similarly, a group of serving cells associated with the SeNB maybe referred to as a secondary cell group (SCG).

Certain aspects of the present disclosure present MC procedures whichinclude procedures to change (add to an SCG, remove from an SCG, ormodify the configuration of) one or more cells of an SeNB, whilemaintaining a current MeNB. As will be described in greater detailbelow, MC procedures may include various options for offloading datacommunications using MC, for example, at the packet level, bearer level,or access packet network (APN) level.

MC procedures may also include handover procedures to change the MeNB,e.g., by transferring the functionality of the MeNB for a UE's MCconfiguration to another eNB, as well as additional aggregationprocedures. The aggregation procedures may include procedures to change(add, remove, or modify) a set of one or more secondary componentcarriers (SCC) of the MeNB and/or an SeNB. In some cases, aggregationmay imply a primary component carrier (PCC) controlling one or moresecondary component carrier (SCCs) with a common media access control(MAC) layer.

The present disclosure provides various options for aggregation andU-plane splitting, such as aggregation within a same node, (e.g.,carrier aggregation) and U-plane splitting across nodes via the radioaccess network (RAN). For example, for multi-connectivity, a data flowmay be split on a per-packet basis or split on a per-bearer basis (e.g.,split over the X2 interface instead of the S1 interface).

In some cases, the U-plane may also be split across nodes via the CN,for example, via a bearer-split using multi-connectivity. That is, a CNsending data via multiple bearers e.g., Bearer A and Bearer B in FIG. 1,to a UE may use multi-connectivity to assign one bearer to an MeNB and asecond bearer to an SeNB, and send data packets to the MeNB and SeNBbased on which bearer each packet is traversing.

Another option for aggregation and U-plane splitting is non-seamlessoffload, which may include offloading to another operator (if allowed),for example, if session continuity is not necessary. This may beconsidered equivalent to per-packet splitting if multi-path transmissioncontrol protocol (MP-TCP) is available, otherwise the split may occur atthe Internet protocol (IP) flow level. Another option is multi-casting(e.g., bi-casting) traffic wherein, for example, each packet is servedby both the MeNB and SeNB for greater reliability.

Aspects of the present disclosure describe several possibleconsiderations for making aggregation and U-plane split decisions. Insome cases, aggregation in a node may utilize a common MAC layer. Theaggregated PCC and SCC(s) may have compatible control channels andtiming requirements, but may not require a separate UL channel (e.g.,for acknowledging transmissions) for the SCC(s).

In some cases, per-packet U-plane splitting performance may be optimizedto support multiple access links across RATs with different latenciesand link error rates. Similarly, per-packet U-plane splittingperformance may be optimized across licensed, shared, and/or unlicensedbands, and for cells sharing the same carrier and/or for cells onseparate carriers.

Example Protocol Stack Configurations for Aggregation and User PlaneSplitting

Different options for U-plane splitting may be described with referenceto wireless communication protocol stacks, such as the Long TermEvolution (LTE) C-plane stack 200 and U-plane stack 210 shown in FIG.2A. In the C-plane, a non-access stratum (NAS) message is received bythe radio resource control (RRC) layer and is passed down to the packetdata convergence protocol (PDCP) layer, radio link control (RLC) layerand media access control (MAC) layer. In the U-plane, an IP packet isreceived by the PDCP layer and passed down to the RLC layer and MAClayer.

As mentioned above, different levels of U-plane splitting are possible,with different corresponding considerations when making routingdecisions. For example, for a per-bearer or per IP flow split, adecision of where to serve each IP packet may be based on a Traffic FlowTemplate (TFT) associated with the bearer or IP flow. In this case, acommon PDCP layer or RLC layer may not be required between differentserving nodes as there is no reordering issue between serving nodes,since all the IP packets for a flow are routed through the same servingnode. That is, because the packets are routed based on which bearer orflow the packets belong to, all of the packets for any given flow arriveat the UE from one serving node, and the receiving UE can determine thecorrect order of the packets from indicators supplied by the node.

When packets of a flow arrive from multiple serving nodes, theindicators (e.g., sequence numbers) used by the nodes may conflict, andthe receiving UE cannot determine the proper order of the packets. Forexample, in the case of a per-bearer or per-IP-flow split, the split mayoccur at a serving gateway (SGW) via an S1 interface (e.g., for MC) orat a packet data network gateway (PGW) or home agent (HA) (e.g., forWLAN interworking), resulting in packets for the bearer or IP flow beingdelivered to multiple serving nodes which may then assign their ownindicators to the packets without coordination. For the UE to reassemblethe packets in the correct order, some coordination or additionalinformation must be provided. As an example, the node at which the splitoccurs may provide packet identifiers that determine a sequence ofpackets for the bearer, irrespective of the serving node that delivers aparticular packet. A RAN-only solution may also be possible via aninterface between serving nodes, e.g., an X2 interface.

For U-plane splitting on a per-packet basis, a common PDCP layer (forMC) across serving nodes may be utilized to reorder the packets in aflow, while RLC reordering may also be possible. In the case of U-planesplitting on a per-packet basis, the per-packet decision of where toserve each PDCP packet may be based on scheduling requirements (e.g.,bandwidth available at transmission times) on each eNB. According tocertain aspects of the present disclosure, flow control may be definedbetween the MeNB and SeNB to allow the MeNB and SeNB to make theper-packet determinations of where to serve each PDCP packet.

In certain systems (e.g., current LTE), mobility and aggregation aregenerally based on the principle that a UE is served by a single servingeNB on the C-plane, meaning that RRC and NAS signaling are only sent tothe UE via a single eNB. In some versions of these systems, a UE mayalso be served by up to 2 serving eNBs on the U-plane, and by multiple(e.g., up to 5 in Release 12 of LTE) cells across the 2 serving eNBs.

FIG. 2B illustrates an example configuration 230 of carrier aggregationfor the U-plane protocol stack for an eNB having a primary componentcarrier (PCC) f1 and secondary component carriers (SCCs) f2-f5 incurrent wireless communication systems (e.g., LTE Rel-10). In carrieraggregation (CA), reconfiguration, addition, and removal of secondarycells (SCells) within a single serving eNB may be performed by the RRCfunction. The primary cell (PCell), belonging to the same eNB, is usedfor transmission of physical uplink control channels (PUCCH), and NASinformation is taken from the PCell. Cross-carrier scheduling, via acarrier indicator field (CIF), allows the physical downlink controlchannel (PDCCH) of a serving cell (e.g., the PCell) to scheduleresources on another serving cell. Unlike SCells, it may not be possibleto remove or deactivate a PCell.

A PCell serving a UE may be changed with a handover procedure (i.e. witha security key change and RACH procedure). For handover from one LTEPCell to another LTE PCell, RRC functions can also add, remove, orreconfigure SCells for usage with the target PCell. As a result, the UEmay be able to handover (HO) to a target eNB and continue CA without there-establishing connections to SCells serving the UE. Re-establishmentof connections by the UE is triggered when the PCell serving the UEexperiences RLF, but not when SCells experience RLF. UEs operating in aCA system generally receive data faster due to the increased availablebandwidth in a CA system than in a system without CA.

FIG. 3 illustrates an example configuration 300 of a dual connectivityprotocol stack linking (via an X2 connection) an MeNB and an SeNB. Theprotocol stack for a particular bearer generally depends on how thatbearer is setup. For example, various alternative types of bearer exist:MCG bearers, split bearers, and SCG bearers. For MCG bearers (e.g., theleft bearer in FIG. 3), the MeNB is U-plane connected to the S-GW via anS1-U interface and the SeNB is not involved in the transport of userplane data for this bearer. For split bearers (e.g., the middle bearerin FIG. 3), the MeNB is U-plane connected to the S-GW via an S1-Uinterface and, in addition, the MeNB and the SeNB are interconnected viaan X2-U interface, allowing both the MeNB and the SeNB to deliverU-plane data to the UE. For SCG bearers (e.g., the right bearer in FIG.3), the SeNB is directly connected with the S-GW via an S1-U interface.

Signaling radio bearers (SRB) are typically of the MCG bearer type and,therefore, use radio resources provided by the MeNB. At least one cellin SCG typically has a configured UL RRC connection, and one of them isconfigured with PUCCH resources, which may be used for controlprocedures (e.g., data scheduling) that do not require the existence ofan SRB. As noted above, re-establishment may be triggered when the PCellexperiences RLF, but not when an SCell experiences RLF. The MeNBmaintains the radio resource management (RRM) measurement configurationof the UE and may decide to request an SeNB to provide additionalresources (serving cells) for a UE (e.g., based on received measurementreports or traffic conditions or bearer types). In this case, the MeNBand the SeNB may exchange information about UE configuration by means ofRRC containers (inter-node messages) carried in X2 messages. In DC, twocell radio network temporary identifiers (C-RNTI) are typicallyindependently allocated to a UE, one for use in communicating with theMCG, and one for use in communicating with the SCG.

Example User Plane Offload Options

As used herein, the term offload generally refers to the breaking out(i.e., offloading) of data at an earlier point in the path. For example,if data is routed from one path (e.g., through an MeNB and an SeNB) to ashorter path (e.g, through an SeNB only). For example, a UE may be saidto be operating with minimal offload for a flow, if all data is routedthrough a GW in the CN via an MeNB. The UE may be said to be operatingwith local offload for a flow, if all data is routed through a LGW inthe MeNB while the UE may be said to be operating with maximum offloadfor the flow if all the data is routed through a LGW in the SeNB anddoes not traverse the MeNB.

As used herein, the term User plane (U-plane) splitting generally refersto how the traffic is delivered from the GW to the UE. As will bedescribed in greater detail below, decisions regarding where to offloadtraffic and how to configure U-plane splitting may be based on the dataservice requirements and other considerations (e.g., available resourcesand radio frequency (RF) conditions of potential offload targets).

FIG. 4 illustrates various U-plane offload options. In a firstconfiguration 410, the GW 140 for U-plane data, such as operatorservices and voice over LTE (VoLTE), may be in the core network (CN). Inthe first configuration, the U-plane data may be described as minimallyoffloaded (from the perspective of the core network), because the commongateway 140 is upstream of the MeNB and SeNB.

In a second configuration 420, the GW may be at the MeNB (shown as localor logical gateway LGW) for traffic requiring “local” session continuitywithin the service area of the MeNB, such as selected internet IPtraffic offload (SIPTO) at the RAN. In the second configuration, the“local” session traffic may be described as being in a greater offload(e.g., more offloaded) than the traffic in the first configurationbecause the local gateway 422 is located at the MeNB, meaning that datahandling (e.g., routing) for such traffic can take place at the MeNBrather than at nodes in the core network.

In a third configuration 430, the LGW 432 is at the SeNB fornon-seamless traffic (e.g., SIPTO at a local network). In the thirdconfiguration, the non-seamless traffic may be described as completely(or maximally) offloaded, as the gateway is located at the SeNB, andthus none of the traffic traverses the MeNB or the network operatorgateway. Mobility for the services provided to the UE decreases as theoffload increases, because mobility (e.g., handovers) are managed by theMeNB, but the offloaded traffic is traversing and even being managed bythe SeNB.

Decisions on where and how to offload data may have significant impactson performance and implementation complexity. For example, data offloadin the RAN may reduce overall U-plane traffic at the CN and enableefficient access to local services. However, this same offload mayimpact user experience for highly mobile UEs due to the need to relocateor modify the gateway functionality if the UE changes cells, and mayalso increase backhaul connectivity requirements for data forwardingbetween cells for local session continuity.

FIG. 5 illustrates three example U-plane splitting options. U-planesplitting configurations generally define how and where bearers areserved by the network and UE for seamless connectivity. Decisionsregarding whether U-plane data is split on a per-packet basis (packetsplitting) or a per-bearer basis (bearer splitting) may be based oncoupling between the MeNB and SeNB. In addition, the decisions may be afunction of UE capability and backhaul availability

As illustrated, in a first configuration 510, U-plane data may be routedto or from the core network GW 140 via the SeNB 130. This is an exampleof bearer splitting in the core network.

A second configuration 520 shows per-bearer U-plane splitting (or simplybearer splitting) in the RAN. That is, the packets are routed based onwhich bearer each packet is for by the core network in configuration 510and by the RAN in configuration 520.

A third configuration 530 shows per-packet U-plane splitting (or simplypacket splitting) in the RAN. As illustrated, in this configuration,some packets for a bearer are served by the MeNB while other packets areserved by the SeNB.

For bearer splitting, there may be no need to route, process and bufferbearer traffic served by the SeNB at the MeNB. As a result, there is noneed to route all traffic to the MeNB, which may allow for lessstringent requirements on the backhaul link between the MeNB and theSeNB (e.g., less bandwidth demands and higher latency tolerated). Inaddition, bearer splitting may provide support of SIPTO and contentcaching at the SeNB, as well as independent protocol stacks on each linkas there is no requirement for coordinated flow control between the twolinks.

In some cases, packet splitting may have advantages over bearersplitting. For example, for bearer splitting the offloading may need tobe performed by a mobility management entity (MME) configuring thetunnels (e.g., IPSec tunnels or other protocol tunnels) at the SGW and,as a result, dynamic changes to the configuration of bearers may belimited and may require SeNB mobility to be visible to the CN. That is,if a UE moves out of the service area (e.g., a cell) of an SeNB, the CNmust be informed so that the CN can reconfigure the bearers for the UE.For bearers handled by the SeNB, handover-like interruption may occurwith SeNB changes, with data forwarding between SeNBs. Further,utilization of radio resources across an MeNB and an SeNB for the samebearer may not be possible in many cases.

Packet splitting may enable CA-like gains across cells and finegranularity load balancing (as routing decisions are made per-packetrather than per-bearer). Packet splitting may also enable more dynamicbearer switching based on cell loading and may also reduce CN signalingas SeNB mobility may be partly or entirely hidden from the CN. That is,the CN may not be informed of a UE moving out of a service area of aparticular SeNB, as the CN forwards the packets to the RAN, and the RANdetermines which SeNB (or the MeNB) delivers the packet to the UE.Further, as routing decisions are made per-packet, no data forwardingbetween SeNBs may be required upon a change of the SeNB (e.g., whenchanging SeNBs, packets may simply not be routed to an SeNB beingde-activated), thus relaxing requirements for SeNB mobility. Inaddition, utilization of radio resources across MeNB and SeNB for thesame bearer may be possible.

In some cases, bearer splitting may have advantages over packetsplitting. For example, packet splitting may require routing, processingand buffering all traffic in the MeNB and may also increase backhaulconnectivity requirements, relative to bearer splitting, for dataforwarding between cells, and packet splitting does not readily supportSIPTO or content caching at the SeNB. In addition, packet splitting mayrequire coordinated flow control and may result in more complex protocolstacks (relative to bearer splitting) to account for different links andover the air (OTA) and backhaul latencies.

Example Control Plane Options

Various RRC functions may be relevant for the SeNB operation used in MCrouting. For example, common radio resource configurations of an SeNB,dedicated radio resource configurations, and measurement and mobilitycontrol for the SeNB, may be relevant to MC routing.

FIG. 6 illustrates example control plane logical architecture optionsfor RRC. In some cases, the RRC packets for the MeNB 120 may be sent tothe MeNB via the SeNB 130 and forwarded over the backhaul (configuration620) and/or vice versa (configuration 610). In this case, the RRCmessaging (or other RAT equivalent signaling) may need to support anaddress scheme over the air (OTA) to identify the target (whether MeNBor SeNB) for the packet.

As illustrated by configuration 610, the RRC logical architecture mayinclude a single RRC instance in an MeNB, wherein any RRC messagesdelivered via an SeNB are tunneled via the MeNB RRC instance. Asillustrated by configuration 620, the RRC logical architecture may alsoinclude separate RRC (or equivalent) instances in the MeNB and the SeNB,for example, with the separate independent instances managing the airlink configuration. In this case, coordination over X2 may be needed forUE configuration, for example, the MeNB and SeNB may coordinate toassign common or mutually compatible discontinuous reception (DRX)parameters to the UE.

In some cases, the RRC functionality allowed in the SeNB may only be asubset of the full RRC functionality (e.g., if only the MeNB managesmobility of the UE in connecting to the SeNB and U-plane splittingconfiguration). In this case, the RRC instance in the MeNB may beconsidered a primary RRC and the RRC instance in the SeNB may beconsidered a secondary RRC. In some cases, the SeNB may be associatedwith a different RAT as compared to the MeNB, which may be similar tohaving separate systems as there may be no requirement for the MeNB tomanage the configuration of the SeNB air link to the UE.

FIG. 7 illustrates C-plane NAS logical architecture options. The NASlogical architecture options include a single NAS instance in an MME702, served by lower layer transport through a single MeNB 120 asillustrated by configuration 710. The protocol stack in the MeNBprovides transport for NAS messages exchanged by the UE with the MME. Inthis logical architecture, NAS messages may or may not be sent throughthe SeNB 130, depending on the RRC logical architecture used with theNAS architecture. NAS messages to be sent through the SeNB are forwardedto the SeNB from the MeNB (for delivery from the MME to the UE), orforwarded to the MeNB from the SeNB (in case of delivery from the UE tothe MME).

A second C-plane NAS logical architecture option is to include anindependent instance in each of the MeNB and the SeNB of a protocollayer capable of delivering messages to a NAS instance in the MME (e.g.,an RRC layer), as illustrated by configuration 720. In the second NASarchitecture, the MME 702 exchanges NAS messages via both the MeNB 120and the SeNB 130. In such an architecture the MME may operate a singleNAS protocol instance with the ability to coordinate separatecommunications with the SeNB and the MeNB. The protocol layerimplemented in the SeNB for communication with the NAS layer in the MMEmay comprise only a subset of the underlying protocol; e.g., an RRClayer in the SeNB may not support all functions of a complete RRCinstance, as described further below.

A particular example implementation of a C-plane NAS and RRC logicalarchitecture may have separate RRC (or equivalent) instances in an MeNBand an SeNB with a single NAS in the MeNB. The separate RRC instancesmay require some coordination over X2 for dedicated and common resourcesin order to serve the UE, although this coordination may be invisible tothe UE. As noted above, the RRC instance in the SeNB may only be asubset of a full RRC (e.g., the RRC of the MeNB may act as a primary RRCwhich manages mobility of the UE to the SeNB and U-plane splittingconfiguration, and the RRC of the SeNB may act as a secondary RRC withlimited functionality, such as having only the ability to providetransport for NAS messages without supporting the mobility and resourcemanagement functions that would normally be present in a fullyimplemented RRC protocol instance). NAS messages from the single NASinstance in the MeNB may be sent to either the MeNB or the SeNB. A newprocedure may be used to reconfigure the SeNB to function as an MeNB fora particular UE, for example, as a “failover” mechanism in the case ofRLF on the MeNB.

Example Control Plane Mobility

FIG. 8 illustrates an example call flow diagram 800 for a C-planemobility procedure, where a DC data path is shown as a dashed line forPDCP aggregation. As illustrated, the C-plane mobility procedure mayoccur in four general phases. The four phases apply for mobility duringboth handover and multi connectivity. The four phases may include a UEmobility configuration phase 802, a RAN mobility preparation phase 804,a mobility execution phase 806, and a mobility completion phase 808.

The UE mobility configuration phase 802 begins with, for example, the UEestablishing a connection and receiving, from the MeNB, a measurementconfiguration. UE mobility configuration allows the RAN to configure theUE to set the RF triggers for mobility. This includes the RF conditionson the serving cell, neighbor cells (both intra and inter RAT), andrelative conditions between the serving and neighbor cells. The UEmobility configuration includes service and context aware events. Forexample, based on a specific traffic type, the UE may performmeasurements on frequencies or other resources to trigger mobilityevents to RATs or channel resources specific to a certain type oftraffic (e.g., a type defined by latency or other QoS aspects, low powerrequirements for the UE, or a content type, e.g., Multimedia BroadcastMulticast Service (MBMS)). In certain aspects, the network may provideconfiguration, including context and service configuration, for a UE todetermine when to perform HO measurements (UE-centric measurementtriggering). In other aspects, the UE provides context and service stateto the network, and the network triggers measurement events based on thestate (network-centric measurement triggering). Both UE- andnetwork-centric measurement triggering may be in use in a single system,e.g., for different event types.

During the RAN mobility preparation phase 804, the UE context isprovided to the SeNB or a target eNB. For example, the UE sends ameasurement report to the MeNB, which makes a mobility decision based onthe measurement report. The MeNB then, for example, sends a mobilityrequest via the X2 connection to the target eNB (the prospective SeNB)to perform admission control. For backward HO, the UE context is sent tothe target eNB before the HO or DC event, for example, triggered basedon the UE measurement report in response to the mobility configuration.For forward HO, the context is sent after the HO event, i.e., sendingthe context is triggered as a pull from the target eNB in response tothe UE establishing a connection at the target eNB and identifying thesource eNB. The backward-HO approach would typically be expected formulti-connectivity mobility events, but the forward-HO approach is alsopossible, Sending the context after the HO or DC event (the forward-HOmodel) may provide a potential for more efficient preparation ofmultiple target eNBs, when compared to sending the context before the HOevent. Moreover, sending the context after the HO or DC event may allowfor differentiation between handovers within a cloud or cluster andhandovers to a BS outside the cloud or cluster. For example, for intracloud handover, coordinated multipoint (CoMP) concepts may be extendedto provide a single logical context across the cloud that does notchange when the point of attachment changes, and actual HO (e.g.,transferring the control-plane function for the UE from one eNB toanother) may only be needed for inter cloud UE mobility.

During the mobility execution phase 806, the UE may establish aconnection at the SeNB or target eNB. The newly established connectionallows UL and DL data to be communicated via the SeNB or target eNB. Forexample, the SeNB sends a mobility request acknowledgement via the X2connection to the MeNB. The MeNB then sends an RRC connectionreconfiguration message to the UE. The UE then synchronizes to the newcell, sends a random access preamble to the SeNB, and receives a randomaccess response from the SeNB. The MeNB then sends the sequence number(SN) status transfer message to the SeNB and begins data forwarding.This approach may provide the potential to perform an inter-cluster HOwhile maintaining IP connections via selected IP traffic offload (SIPTO)and local IP access (LIPA). In addition, this approach may allowoptimized procedures to assign a new IP address on HO, as well asenabling more make before break (as compared to current HO techniques)for mission critical applications, due to multi connectivity. MPTCP canbe used (e.g., end-to-end) if required, or applications can bemulti-homed or designed to handle IP address changes.

During the mobility completion phase 808, the network moves any tunnelsassociated with the SeNB or target eNB and the SGW to point directly tothe SeNB or target eNB and in the case of HO, releases resources on thesource eNB.

Example Admission Control and Load Balancing

As noted above, as a part of managing UE connectivity to the RAN, anMeNB may make decisions, for the UE, regarding aggregation and U-planesplitting options. When a set of services change on an SeNB or a UEcontext changes, an MeNB may want perform load balancing or admissioncontrol for the new services based on the current configuration of theaggregation and U-plane split for the UE.

Contexts may include, for example, Mobility (for example, car, train,bike, plane, pedestrian, or stationary), location (including outdoors orindoors, at work or home, in a meeting, in a conference), accessibilityand UE state (for example, on the user's body, separate from the usersuch as for charging, screen on/off, in holster pocket, active use).Services may include, for example, applications (for example, Facebook,YouTube) or service types (for example, voice, streaming, or downloads).

In some cases, the MeNB may be aware that the services are activated,for example, if the U-plane for the data is via the MeNB. For example,the MeNB may be aware that the services are activated in the followingcases: aggregation within a node (for example, carrier aggregation),U-plane split across nodes via the RAN (for example, multi-connectivityusing packet split or bearer split over X2 connection instead of S1connection), or when multi-casting traffic (for example, each packet isserved by both the MeNB and SeNB for greater reliability).

In certain cases, the MeNB may be aware of the service, for example, ifthe UE activates a new bearer for the service the MME may inform theMeNB of the service requirements as a part of the configuration of thebearer at the MeNB. The MeNB may see the bearer activation and may be,in certain cases, responsible for the configuration and handover of thebearer to the SeNB. On the other hand, when services are activatedwithin an existing bearer or U-plane, then no C-plane signaling may bepresent to indicate that the service is activated. In certain cases,where traffic may only be visible at the SeNB, techniques such as deeppacket inspection (DPI) may not be possible since the traffic does notgo through the MeNB.

In other cases, the MeNB may not be aware of the UE services. Forexample, the MeNB may not be aware of the UE services in the case ofU-plane split across nodes via the CN (e.g., multi connectivity-bearersplit) or in the case of non-seamless offload (NSO). Cases of NSO mayinclude offload to another operator or access network if, for example,the offload is allowed by the other operator and no session continuityis required for the service.

Aspects of the present disclosure provide a framework to enable the MeNBto be aware of the active services and context for the UE in order todetermine the load balancing and admission control for these services.

Aspects of the present disclosure provide various options fordetermining that a service (e.g., a new service) is active at the MeNB.Some of these options apply to cases in which an MeNB determines that anew service is active (or an existing service is modified) via detectionat the gateway (PGW or SGW), for example, based on DPI. In this case,the PGW or SGW may label packets directly or indirectly as correspondingto a service in the general packet radio service (GPRS) tunnelingprotocol (GTP) tunnel sent to the MeNB or SeNB. For example, the bearerID may be associated with a quality of service class indicator (QCI) andpackets arriving on the bearer may indicate a new service is active.

In certain cases when the new service is a bearer and is associated witha specific service, the bearer may be established when the service isactivated. Thus, in this case, the MeNB may see the S1 messages toestablish the bearer and may also move the bearer to the SeNB.Alternatively, the GTP tunnel may include a service label informationelement (IE) which indicates the service to the tunnel end-point. In thecase of the GTP tunnel terminating at the MeNB, the MeNB can use thepresence of the packets to determine a service on the UE. In the case ofthe GTP tunnel terminating at the SeNB, the SeNB can inform the MeNBover the backhaul of the service on the UE.

As an alternative or in addition, the PGW or SGW may inform the MME(e.g., via CN signaling) that packets for a service are detected. Forexample, the PGW may initiate a dedicated bearer activation procedurefor the detected service. In this case, the MME may inform the MeNBdirectly of the service by sending a context update to the MeNB aboutthe set of services on the UE. The MME may also inform the MeNBindirectly, for example, if the MME establishes a new dedicated bearerfor the UE at the MeNB for example, as initiated by the PGW or SGWsignaling.

Other options for determining that a service is active at the MeNB applyto cases in which services (or context changes) are initiated at the UE.In this case, the UE may inform the MeNB or SeNB of the set of serviceseither explicitly or implicitly. For the implicit case, the UE may useNAS signaling to request a service. For example, the UE may initiate aPDN connection for the service which the MME will determine to allow ordeny based on the UE subscription information and the current networkloading. For the explicit case, the UE may use RRC or NAS signaling toindicate the active set of services or context of the UE as will bedescribed further below.

Aspects of the present disclosure also provide various options for loadbalancing the set of services at the MeNB (and/or the SeNB). Forexample, such options may include load balancing messages sent over thebackhaul. In this case, the MeNB and SeNB may exchange reports over thebackhaul per UE and per service to determine the correct load balancingat the SeNB and MeNB. The MeNB may use the reports to select among thedifferent options for serving the UE based on services and context ofthe UE. The options for serving the UE may include, for example,handover, CA, MC, or non seamless offload.

The MeNB may also use the reports to enable an energy efficient networkoperation based on active services. For example, the MeNB may activateand deactivate RATs in the network based on services being detected andUE measurement reports. If the load on an SeNB falls below a thresholdand the MeNB has sufficient capacity, the MeNB may remove all the MCtraffic from the SeNB and deactivate the SeNB. Similarly, if the load onthe MeNB goes above a threshold, the MeNB may activate certain RATs oncertain SeNBs and HO or use U-plane split options to serve some of thetraffic on the SeNBs, based on the active services and UE context.

In some cases, UE reports used for load balancing and/or admissioncontrol may be sent over the air. The MeNB may configure UE reports tobe sent over the air, for example, if no X2 or equivalent backhaulinterface exists to the SeNB to exchange load or service relatedinformation about the UE. In addition to measurement reports on theradio frequency (RF) related conditions, the UE may inform the MeNB ofthe quality of service (QoS) related measurement reports related to theservices and context for the UE at the SeNB. Thus, based on suchreports, the MeNB may determine if the U-plane split needs to beadjusted. The reports may be per service, including event reporting whennew services are activated within an existing bearer or APN (forexample, services that would not have any C-plane signaling to the MeNBsuch that the MeNB would not be aware of them unless the UE or SeNBsends an indication).

Certain aspects of the present disclosure provide procedures for the UEto indicate the active set of services or context. The set of servicesand UE context can be provided to the network at the time the UEestablishes a connection to register, for example, with a tracking areaupdate (TAU)/location area update (LAU) and attach. The set of servicesand UE context can be provided to the network at the time the UEconnects for data services (service request). The UE may also provideservices and/or UE context in the event of a change (e.g., with somehysteresis to limit unnecessary ping-ponging).

In some cases, the UE may provide a time estimate in the set of servicesand context that, for example, may indicate when the set of services orcontext may go into effect or for how long the service or context isexpected to last. As noted above, the set of services and context can beprovided via NAS signaling to the MME or via RRC signaling to the MeNBor SeNB.

FIG. 9 shows an example call flow diagram 900 that illustrates exampleprocedures for providing the set of service and UE context to the MME,in accordance with aspects of the present disclosure.

As illustrated, the UE may send an RRC ULInformationTransfer message (1)along with a NAS message including the set of services and UE contexttowards the MME encapsulated in the RRC message. The eNB forwards theNAS message (2) in a UL NAS Transport container to the MME.

The MME may then optionally performs admission control (3) on the set ofservices to determine what policy is to be sent to the MeNB or sourceeNB or how to support the service requirements given the indicated setof services and UE context. The MME then sends the S1-AP UE ContextModification Request (4) to the MeNB or source eNB to indicate thepolicy and service requirements for the UE based on the context and setof services.

Optionally, the MME may modify existing bearers or initiate newdedicated bearers with the PGW/SGW to support the services and context.The MME may also send the context and set of services to the eNB. As analternative, the MME may indicate the behavior of the RAN with respectto the services and UE context in the Subscriber Profile ID IE.

In addition, the eNB may send an RRCConnectionReconfiguration message(5) to the UE to modify the bearers or UE configuration in response tothe S1-AP UE Context Modification Request (4). The UE may then send anRRCConnectionReconfigurationComplete message (6) in acknowledgement ofthe RRCConnectionReconfiguration message.

FIG. 10 shows a call flow diagram 1000 that illustrates exampleprocedures for providing the set of service and UE context to the RAN,in accordance with aspects of the present disclosure.

As illustrated, the UE may send the RRC ULInformationTransfer message(1) including the set of services and UE context to the MeNB or sourceeNB in the RRC message. Optionally, the eNB forwards the services andcontext to the MME in a UE Context and Services Indication message (2).The remaining operations 3-6 of FIG. 10 may be performed in the samemanner as described above, with reference to FIG. 9.

FIG. 11 illustrates example operations 1100 for managing at least onedata flow between a core network and a mobile device, in accordance withaspects of the present disclosure. The operations 1100 may be performedby a mobile device, such as a UE.

The operations 1100 begin, at 1102, by determining whether at least oneof the data flow or a service related to the data flow should bereported. At 1104, the mobile device sends a report to a first nodebased on the determination, wherein the report identifies at least oneof the data flow or service and indicates a packet data network (PDN)connection or bearer associated with the service or data flow.

In some cases, the operations described herein may only be performedwhen applicable. For example, in certain aspects, the determining andsending are performed in response to some type of triggering event.Examples of such triggering events include identifying that the dataflow is activated or identifying that an amount of data is above athreshold.

In some cases, the mobile device (UE) receives a configuration whichindicates which data flows to report. In some cases, the determining andsending are performed in response to the configuration. In some cases,the determining is a function of a location of an aggregation point forthe data flow (e.g., if the data flow is not received by the firstnode). In some cases, the report is sent using at least one of radioresource control (RRC) or non-access stratum (NAS) signaling. In somecases, the data flow comprises a new data flow. In some cases, the dataflow comprises data for an application. In some cases, the data flowcomprises data for a service.

FIG. 12 illustrates example operations 1200 for managing at least onedata, in accordance with aspects of the present disclosure. Theoperations 1200 may be performed by a second node that, for example, mayprovide MC to a UE, such as an MeNB.

The operations 1200 begin, at 1202, by determining a data flow is activefor a bearer or a packet data network (PDN) connection. At 1204, thesecond node decides, based on one or more service requirements of thedata flow, whether to serve the data flow at the second node or a firstnode. At 1206, the second node sends, to the first node, a request foradmission of the data flow.

According certain aspects, the request for admission comprises anindication of a protocol layer for aggregation of the data flow. In somecases, the first node and the second node operate using different RATs.In some cases, the data flow comprises a new data flow. In some cases,the second node transmits a configuration which indicates which dataflows to report. In some cases, the data flow comprises data for anapplication. In some cases, the data flow comprises data for a service.

FIG. 13 illustrates example operations 1300 for performing admissioncontrol on at least one data flow, in accordance with aspects of thepresent disclosure. The operations 1300 may be performed, by a firstnode (providing MC to a UE), such as an SeNB.

The operations 1300 begin, at 1302, by receiving, from a second node, arequest for admission of the data flow for a bearer comprising aplurality of data flows. At 1304, the first node evaluates availabilityof resources at the first node to serve the data flow with the bearer.At 1306, the first node indicates to the second node whether admissionis granted to the at least one data flow based at least in part on theevaluated availability of resources.

According certain aspects, the request for admission comprises anindication of a protocol layer for aggregation of the data flow. In somecases, the evaluating relates to resources managed by protocol layersbelow a protocol layer of a flow split or a packet split for aggregationat the first node. In some cases, the first node and the second nodeoperate using different RATs. In some cases, the evaluating availabilityof resources at the first node to serve the data flow comprisesdetermining resources available to accept data flows from the secondnode. In some cases, the first may determine that a new data flow isactive; and send a message to the second node based on thedetermination. In some cases, the data flow comprises data for anapplication. In some cases, the data flow comprises data for a service.

FIG. 14 illustrates example operations 1400 for performing loadbalancing, in accordance with aspects of the present disclosure. Theoperations 1400 may be performed by a first node, for example, operatingas an SeNB.

The operations 1400 begin, at 1402, by the first node determining thatat least one data flow is active for an existing bearer or a new packetdata network (PDN) connection, wherein the data flow has an associatedaggregation layer of a protocol stack of the first node. At 1404, thefirst node evaluates the availability of resources at the first node toserve the data flow, wherein the evaluating relates to resources managedby at least one protocol layer that is below the associated aggregationlayer of a protocol stack of the first node. At 1406, the first nodetransmits, to a second node, a message indicating the availability ofresources at the first node for data flows associated with the secondnode and for data flows not associated with the second node.

According to certain aspects, the message indicates a need for reducinga resource load on the first node for the at least one data flow. Insome cases, the first node may receive a request to terminate serving atleast one data flow. In some cases, the first node may receive a requestto deactivate a carrier or radio access technology (RAT), wherein activedata flows are released via a handover (HO) or a deactivation of theconnection with a mobile device associated with the at least one dataflow. In some cases, the first node may deactivate a carrier or RAT ifno more data flows are served on that carrier or RAT.

In some cases, the evaluating the availability of resources at the firstnode to serve the data flow comprises comparing a resource loadassociated with the data flow to a threshold. In some cases, the firstnode has previously received from the second node a request foradmission for the data flow; and the message indicates the availabilityof resources at the first node for the data flow. In some cases, thedata flow includes a new data flow. In some cases, the data flowcomprises data for an application. In some cases, the data flowcomprises data for a service.

FIG. 15 illustrates various components that may be utilized in a MCenabled wireless device 1500 capable of operating in accordance withaspects provided herein. The wireless device 1500 may, for example, beone implementation of UE 110 shown in FIG. 1.

The wireless device 1500 may include one or more processors 1504 whichcontrol operation of the wireless device 1500. The processors 1504 mayalso be referred to as central processing units (CPUs). The processors1504 may perform, or direct the UE in managing data flows, as describedabove with reference to FIG. 11. Memory 1506, which may include bothread-only memory (ROM) and random access memory (RAM), providesinstructions and data to the processors 1504. A portion of the memory1506 may also include non-volatile random access memory (NVRAM). Theprocessors 1504 typically perform logical and arithmetic operationsbased on program instructions stored within the memory 1506. Theinstructions in the memory 1506 may be executable to implement themethods described herein.

The wireless device 1500 may also include radios 1510 and 1512 tocommunicate via multiple RATs for MC. Each radio may, for example,include a transmitter and receiver, and any other “RF chain” componentsto allow transmission and reception of data between the wireless device1500 and different RATs. While two radios are shown for two RATs, as anexample only, more than two radios may be included (e.g., to supportmore than two RATs). Each radio may communicate via a single or aplurality of antennas 1516.

The wireless device 1500 may also include a signal detector 1518 thatmay be used in an effort to detect and quantify the level of signalsreceived by the transceiver 1514. The signal detector 1518 may detectsuch signals as total energy, energy per subcarrier per symbol, powerspectral density and other signals. The wireless device 1500 may alsoinclude a digital signal processor (DSP) 1520 for use in processingsignals.

FIG. 16 illustrates various components that may be utilized in a basestation 1200 capable of participating in communication with a MC enabledwireless device. The base station 1600 may, for example, be oneimplementation of MeNB 120 or SeNB 130 shown in FIG. 1.

The base station 1600 may include one or more processors 1604 whichcontrol operation of the base station 1600. The processors 1604 may alsobe referred to as central processing units (CPUs). The processors 1604may manage data or perform admission control or load balancing, asdescribed above with reference to FIGS. 12-14. Memory 1606, which mayinclude both read-only memory (ROM) and random access memory (RAM),provides instructions and data to the processors 1604. A portion of thememory 1606 may also include non-volatile random access memory (NVRAM).The processors 1604 typically perform logical and arithmetic operationsbased on program instructions stored within the memory 1606. Theinstructions in the memory 1606 may be executable to implement themethods described herein (e.g., for MeNBs and SeNBs serving a DC UE),such as managing data or performing admission control or load balancing,as described above with reference to FIGS. 12-14.

The base station 1600 may also include one or more radios 1610, forexample to communicate with a UE via one or more RATs. Each radio may,for example, include a transmitter and receiver, and any other “RFchain” components to allow transmission and reception of data betweenthe base station 1600 and different UEs. Each radio may communicate viaa single or a plurality of antennas 1616. The base station 1600 may alsoinclude an interface 1612 for communicating with other base stations(e.g., via an X2 backhaul connection) or a core network (e.g., via an S1connection).

The base station 1600 may also include a signal detector 1618 that maybe used in an effort to detect and quantify the level of signalsreceived by the transceiver 1614. The signal detector 1618 may detectsuch signals as total energy, energy per subcarrier per symbol, powerspectral density and other signals. The base station 1600 may alsoinclude a digital signal processor (DSP) 1620 for use in processingsignals.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed above is an illustration of exemplary approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of steps in the processes may be rearranged. Further, somesteps may be combined or omitted. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise or clearfrom the context, the phrase, for example, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, forexample the phrase “X employs A or B” is satisfied by any of thefollowing instances: X employs A; X employs B; or X employs both A andB. In addition, the articles “a” and “an” as used in this applicationand the appended claims should generally be construed to mean “one ormore” unless specified otherwise or clear from the context to bedirected to a singular form. A phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover: a, b, c, a-b, a-c, b-c, and a-b-c.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed as a means plus functionunless the element is expressly recited using the phrase “means for.”

What is claimed is:
 1. A method of wireless communication by a secondnode for managing a data flow, comprising: receiving an indication ofone or more service requirements of the data flow that is active for abearer or a packet data network (PDN) connection; deciding, based on theone or more service requirements of the data flow, whether to serve thedata flow at the second node or a first node; and sending, to the firstnode, a request for admission of the data flow based on the decision,wherein the request for admission comprises an indication of a protocollayer for aggregation of the data flow.
 2. The method of claim 1,wherein the first node and the second node operate using different radioaccess technologies (RATs).
 3. The method of claim 1, wherein the dataflow comprises a new data flow.
 4. The method of claim 1, furthercomprising transmitting a configuration which indicates which data flowsto report.
 5. The method of claim 1, wherein the data flow comprisesdata for an application.
 6. The method of claim 1, wherein the data flowcomprises data for a service.
 7. A second node for managing a data flow,comprising: means for receiving an indication of one or more servicerequirements of the data flow that is active for a bearer or a packetdata network (PDN) connection; means for deciding, based on the one ormore service requirements of the data flow, whether to serve the dataflow at the second node or a first node; and means for sending, to thefirst node, a request for admission of the data flow based on thedecision, wherein the request for admission comprises an indication of aprotocol layer for aggregation of the data flow.
 8. The second node ofclaim 7, wherein the first node and the second node operate usingdifferent radio access technologies (RATs).
 9. The second node of claim7, wherein the data flow comprises a new data flow.
 10. The second nodeof claim 7, further comprising means for transmitting a configurationwhich indicates which data flows to report.
 11. The second node of claim7, wherein the data flow comprises data for an application.
 12. Thesecond node of claim 7, wherein the data flow comprises data for aservice.
 13. A non-transitory computer-readable medium for managing adata flow having instructions stored thereon, to be executed by aprocessor, for causing a second node to: receive an indication of one ormore service requirements of the data flow that is active for a beareror a packet data network (PDN) connection; decide, based on the one ormore service requirements of the data flow, whether to serve the dataflow at the second node or a first node; and send, to the first node, arequest for admission of the data flow based on the decision, whereinthe request for admission comprises an indication of a protocol layerfor aggregation of the data flow.